Geographic survey system for vertical take-off and landing (vtol) unmanned aerial vehicles (uavs)

ABSTRACT

A method of unmanned aerial vehicle (UAV) operation, including: receiving from a customer a first data request, the first data request having: a first geographic coverage area; and a refresh rate for the first geographic coverage area; planning a first plurality of flight missions to accomplish the first data request; uploading flight missions data representing the first plurality of flight missions into a UAV pod; and deploying the UAV pod.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/040,957, filed Feb. 10, 2016, which claims priority to and thebenefit of U.S. Provisional Patent Application No. 62/115,033, filedFeb. 11, 2015, the contents of which are hereby incorporated byreference herein for all purposes.

TECHNICAL FIELD

The field of the invention relates to unmanned aerial vehicle (UAV)systems, and more particularly to systems for operating a UAVautonomously.

BACKGROUND

Aerial geographic survey work for the agricultural and oil industriesmay be accomplished using unmanned aerial vehicles (UAVs) that generallyreduce costs associated with such activities. Unfortunately, the desiredgeographic coverage area for the survey work may exceed the operationalcapabilities of the UAV for any single flight. A separate challenge mayexist in that the geographic coverage area may also be located in aremote area, making retrieval of the survey data more difficult betweensurvey flights.

A need continues to exist for extending the operational capabilities ofUAVs and facilitating survey data retrieval in remote geographic areas.

SUMMARY

A method of unmanned aerial vehicle (UAV) operation includes receivingfrom a customer a first data request, the first data request including afirst geographic coverage area and a refresh rate for the firstgeographic coverage area, planning a first plurality of flight missionsto accomplish the first data request, uploading flight missions datarepresenting the first plurality of flight missions into a UAV pod, anddeploying the UAV pod. The first data request may also include one of aground resolution or ground surface distance (GSD). The method may alsoinclude providing a two-rotor UAV with flight mission data for one ofthe first plurality of flight missions from the UAV pod, launching thetwo-rotor UAV from the UAV pod to perform the one of the first pluralityof flight missions, receiving the two-rotor UAV on the UAV pod, andreceiving in the UAV pod a first flight survey data obtained from theone of the first plurality of flight missions from the two-rotor UAV. Insuch embodiments, the method may include transmitting the first flightsurvey data from the UAV pod. The method may include providing the UAVwith second flight mission data representing a second one of theplurality of flight missions from the UAV pod, autonomously launchingthe two-rotor UAV from the UAV pod to perform the second one of thefirst plurality of flight missions, receiving the two-rotor UAV on theUAV pod after completing the second one of the first plurality of flightmissions, and receiving a second survey data in the UAV pod from the UAVso that the launching and receiving of the two-rotor UAV to accomplishthe second one of the plurality of flight missions happens autonomouslyand without active human intervention. In such embodiments, the methodmay include providing the second flight survey data from the UAV pod orreceiving the first and second survey data from the UAV pod. In suchembodiments, the receiving the first and second survey data from the UAVpod may include receiving the first and second survey data wirelessly ata remote operational support center. Alternatively, the receiving of thefirst and second survey data from the UAV pod may include removingphysical memory from the UAV pod. The method may further includeperforming data analysis of the first and second survey data andproviding the data analysis to the customer. In such embodiments, themethod may include providing the two-rotor UAV with a third flightmission data representing a third one of the plurality of flightmissions from the UAV pod and receiving the two-rotor UAV on a secondUAV pod. The method may also include receiving a second two-rotor UAV inthe second UAV pod or retrieving the UAV pod, uploading a second flightmissions data representing a second plurality of flight missions intothe UAV pod to accomplish a second data request, and re-deploying theUAV pod. The method may also include providing a second two-rotor UAVwith a third flight mission data representing a third one of the firstplurality of flight missions from the UAV pod and may includeautonomously launching the second two-rotor UAV from the UAV pod toperform the third one of the first plurality of flight missions,receiving the second two-rotor UAV on the UAV pod after completing thethird one of the first plurality of flight missions, and receiving athird survey data in the UAV pod from the second two-rotor UAV so thatthe launching and receiving of the second two-rotor UAV to accomplishthe third one of the plurality of flight missions happens autonomouslyand without active human intervention.

An unmanned aerial vehicle (UAV) operational system may include a UAVpod having a pod memory and a pod processor, the pod memory storing afirst plurality of UAV flight mission information that is adequate tosurvey a geographic coverage area at a predetermined refresh rate and aUAV seated in the UAV pod, the UAV having a UAV memory storage and a UAVprocessor, the UAV memory storing one of the first plurality of UAVflight missions so that each one of the plurality of UAV flight missionsrepresents a launch, survey and landing of the UAV. The system may alsoinclude survey data from at least one of the first plurality of UAVflight missions stored in the pod memory or survey data from at leastone of the first plurality of UAV flight missions stored in a second podmemory so that the second pod memory includes portable memory detachablyconnected to the UAV pod. The UAV pod may additionally include atransceiver in communication with the pod processor, the pod processorconfigured to transmit the survey data to an operational support centerpositioned remotely from the UAV pod. The system may also include acustomer support center configured to receive a first data request froma customer via electronic communications and wherein the first datarequest also includes a first geographic coverage area and a refreshrate for the first geographic coverage area. In such embodiments, thefirst data request may also include one of a ground resolution or groundsample distance (GSD). In embodiments, the system includes a transceiverin the UAV, the transceiver configured to communicate with the UAV pod.

A method of migrating unmanned aerial vehicle (UAV) operations betweengeographic survey areas may include uploading a first plurality offlight missions into a first UAV pod, deploying the UAV pod,autonomously launching the UAV from the UAV pod a plurality of times toperform the first plurality of flight missions, providing first surveydata from the UAV to the UAV pod, autonomously migrating the UAV fromthe first UAV pod to a second UAV pod, receiving a second plurality offlight missions in a second UAV pod, providing the UAV with one of thesecond plurality of flight missions from the second UAV pod,autonomously launching the UAV from the second UAV pod a plurality oftimes to perform the second plurality of flight missions, and providinga second survey data from the UAV to the second UAV pod so that theautonomous migrating of the UAV to accomplish the first and secondsurvey data happens autonomously and without active human intervention.In other embodiments, the method may also include performing dataanalysis of the first and second survey data and providing the dataanalysis to the customer.

BRIEF DESCRIPTION OF THE DRAWINGS

The components in the figures are not necessarily to scale, emphasisinstead being placed upon illustrating the principals of the invention.Like reference numerals designate corresponding parts throughout thedifferent views. Embodiments are illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which:

FIG. 1 is a perspective view of one embodiment of a UAV pod that mayhouse and protect an extended range VTOL UAV to accomplish multipleautonomous launches, landings and data retrieval missions;

FIG. 2 is a perspective view of the two-rotor UAV first illustrated inFIG. 1;

FIG. 3 illustrates the UAV pod 100 in its open configuration;

FIG. 4 is a data flow diagram illustrating information flow from acustomer requesting data, to a customer support center, an operationalsupport center and to a UAV in a UAV pod and back again;

FIG. 5 is a data flow diagram illustrating another embodiment of theflow of information from a customer requesting data, through a customersupport center to an operational support center, to a UAV in a UAV podand back again to the customer;

FIG. 6 is a flow diagram illustrating one embodiment of use of the UAVpod and UAV system by a customer;

FIG. 7 shows a pod that due to its rural location lacks a wireless dataconnection and the UAV 2602 has flown from its pod to loiter above ahouse to be within range of the house's WiFi connection;

FIG. 8 is a flow diagram illustrating one embodiment of a method ofconducting flight missions for the UAV;

FIG. 9 is a block diagram illustrating the use of a plurality of UAVpods with only one UAV to extend the possible geographic survey areafrom what would otherwise exist with only one UAV;

FIG. 10 is a UAV pod and associated UAV provided with a plurality ofmissions that cover a rectangular coverage area; and

FIG. 11 illustrates two extended coverage survey areas that may beserviced using only one UAV or a limited number of UAVs.

DETAILED DESCRIPTION

A vertical takeoff and landing (VTOL) unmanned aerial vehicle (UAV)system is disclosed that provides for improved remote geographic surveycapabilities. Multiple autonomous missions launches and landings may beaccomplished using a two-rotor VTOL UAV that is capable of efficienthorizontal flight.

More particularly, a geographic survey method is described that mayinclude receiving a first data request from a remote customer, with thefirst data request including a first geographic coverage area and arefresh rate for the first geographic coverage area, planning a seriesof UAV flight missions to accomplish the first data request, uploadingflight missions data representing the series of flight missions into aVTOL UAV pod (referred to herein simply as a “UAV pod”), and thendeploying the UAV pod to a remote site for extended and autonomoussurvey work by the enclosed two-rotor UAV, such as through the use ofmultiple autonomous launches, landings and data retrieval missions. Inits broadest sense, the system may be accomplished using a single UAVpod and selectively enclosed two-rotor VTOL UAV for efficient long-rangesurvey work. In other embodiments, one or more two-rotor UAVs may beused and shared with one or more VTOL UAV pods to extend the autonomoussurvey range and coverage of the UAVs between adjacent or non-adjacentgeographic survey regions.

The present invention allows for a customer to make a data requestrelated to a geographic coverage area and a refresh rate related to thatgeographic coverage area. A UAV accomplishes a series of flight missionsrelated to the customer data request and collects flight missions data.The flight missions data is processed and provided to the customer.

Exemplary UAV pod and UAV Structure

FIG. 1 is a perspective view of one embodiment of a UAV pod that mayhouse and protect an extended range VTOL UAV to accomplish multipleautonomous launches, landings and data retrieval missions. Theillustrated system 100 has a winged two rotor UAV 102 seated on alanding surface 104 of an interior 106 of the UAV pod 108. The UAV 102is seated in a vertical launch position to facilitate later launch outof the UAV pod 108. The UAV pod 108 may selectively enclose the UAV 102,such as through the use of a UAV pod protective cover 110. The cover 110may be a two-part hinged cover that is operable to close to protect theUAV 102 from the external environment or to open to enable launch of theUAV 102. The UAV pod 108 may have a short-range UAV pod transceiver 112that may be seated in a compartment below the landing surface 104,within their own separate compartments, or may be seated elsewherewithin the UAV pod 108 for protection from the external environment. TheUAV pod transceiver 112 may receive UAV flight telemetry such as UAVflight and trajectory information, UAV battery status information andsensor data (such as video), and other data transmitted by the UAV 102.The UAV pod transceiver 112 may also transmit flight control data suchas navigation (e.g., re-routing instructions) to the UAV 102. A UAV podprocessor 114 may also be housed within the UAV pod 108 to accomplish,among other functions, providing the UAV 102 with a plurality ofmissions, receiving flight survey data from the UAV 102, monitoring theUAV pod 108 for overhead obstacles, monitoring the external environmentsuch as the weather through the weather sensor, monitoring thetrajectory of the UAV 102, and providing navigation instructions to theUAV 102 in response to receiving UAV battery status or other flightwarning condition data inputs.

A UAV pod memory 116 may also be housed within the UAV pod 108 forstoring UAV flight mission information and geographic survey data. Abattery 118 may be enclosed in the UAV pod for recharging the UAV 102and for providing power to the UAV pod 108 such as for use by theprocessor 114 and cover motor (not shown). The battery 118 may berechargeable such as through solar panels 119, or may be a permanentbattery such as a 12-Volt deep cycle marine battery. In an alternativeembodiment, the battery 118 may be a fuel cell. In some embodiments, theUAV pod 108 will use the solar panels 119 to charge the battery 118 tolater charge the battery of the UAV 102. Typically, the UAV pod 108 willbe charging the battery 118 while the UAV 102 is out of the pod 108executing a mission and will recharge the UAV 102 upon its return to theUAV pod 108.

A weather sensor 120 in communication with the UAV pod processor mayextend from an exterior of the UAV pod 108 to enable accuratemeasurement of the external environment, such as wind speed, temperatureand barometric pressure. A proximity sensor or sensors may also beprovided (122, 124) and in communication with the UAV pod processor 114to enable go and no-go flight decisions based on the proximity of anyobjects or other obstructions positioned over the UAV pod cover 110. TheUAV pod 108 is preferably weather hardened to enable extended outdooruse regardless of weather variations.

FIG. 2 is a perspective view of the two-rotor UAV 102 first illustratedin FIG. 1. The UAV 102 has only two rotors 202 though enabling verticaltakeoff and landing (VTOL) missions out of the UAV pod 108 (see FIG. 1).The UAV 102 has a UAV transceiver 204 within a UAV fuselage 206. A UAVprocessor 208 is also seated in the UAV 102 and in communication withthe UAV transceiver 204. The UAV 102 also includes a battery 209 forproviding power to the rotor motors and the electronics, including theprocessor 208. The UAV processor 208 is configured to receive aplurality of flight mission information that may include waypoints,altitude, flight speed, sensor suite configuration data, launch day/timeand mission weather sensor go and no-go parameters. The UAV 102 may havea variety of electrical optical (EO) sensors 210, such as LiDAR, RADAR,infrared, visible-spectrum cameras, or other active or passive sensorsthat may be used to detect soil moisture, crop density, crop health,terrain, or other objects or qualities of interest. The UAV 102 may havea rear landing gear 212 extending off of a rear of the fuselage 206 thatmay be used in combination with UAV engine nacelles 214 to enable afour-point landing for more stable landings on the UAV pod 108 (see FIG.1). The landing gear 212 may also function as a flight surface oraerodynamic surface, such as a vertical stabilizer, providing corrective(passive) forces to stabilize the UAV 102 in flight, such as tostabilize in a yaw direction. The UAV 102 may have wings 215 to providethe primary source of lift during the UAV cruise (e.g., horizontalflight), while the two rotors 202 provide the primary source of liftduring the VTOL phases of UAV flight. This combination of wing and rotoruse allows for efficient flight while collecting flight survey data,which increases the range and/or duration of a particular flight whilealso allowing the UAV 102 to land and take off from the relatively smallUAV pod 108 (see FIG. 1) landing area. In one embodiment, the UAV 102may take off and land vertically using the two rotors 202 thatthemselves are operable to lift the UAV 102 vertically upwards,transition the UAV 102 to horizontal flight to conduct its survey orother flight mission, and then transition it back to vertical flight toland the UAV 102 vertically downwards, with attitudinal control for theUAV 102 in all modes of flight (vertical and horizontal) coming entirelyfrom the rotors 202 (as driven by a means of propulsion) without thebenefit or need of aerodynamic control surfaces, such as ailerons, anelevator, or a rudder. One such UAV 102 is described in internationalpatent application number PCT/US14/36863 filed May 5, 2014, entitled“Vertical Takeoff and Landing (VTOL) Air Vehicle” and is incorporated byreference in its entirety herein for all purposes. Such a UAV 102benefits from a more robust structure by reducing the opportunity fordamage to control surfaces (i.e., there aren't any), and may be madelighter and with less complexity.

The UAV 102 may also be provided with a rearward facing tang 216extending off of a rear portion 218 of the fuselage 206 in lieu of or inaddition to rear landing gear 212. Such rearward-facing tang 216 may bemetallic or have metallic contacts for receipt of electrical signals(i.e., data) and/or power for charging the UAV's battery 209.

FIG. 3 illustrates the UAV pod 108 in its open configuration. In FIG. 3,the UAV 102 is illustrated in its vertical configuration and seated on alanding surface 104 of the UAV pod 108. The UAV 102 is shown positionedat least generally aligned with the rectangular dimensions of the UAVpod 108. In embodiments, the landing surface 104 is rotatable toposition the UAV. The cover 110 is open to enable unobstructed launch,and later landing, of the UAV 102. The cover 110 is illustrated withside portions 300 and top portions 302, with hinges 304. In analternative embodiment, only the top portions 302 are hinged to enableunobstructed launch of the UAV 102. Alternatively, the top portions 302may translate out of the flight path linearly or using a mechanism andmotion so that the UAV is free to launch. In one embodiment, the landinggear 212 may be omitted and the UAV 102 may be guided into and out ofone or more slots, guide rails, channels, or other guiding structure toboth secure the UAV 102 during its landed state and enable landing. Theweather sensor 120 may be coupled to the cover 110 or may extend off theside of the UAV pod 108 (not shown). Also, although the UAV pod 108 isillustrated having a rectangular cross-section and a box—like structure,the UAV pod 108 may take the form of a dome-shaped structure or otherconfiguration that enables stable placement and protection for theselectively enclosed UAV. The cover 110 can include solar panels on itsexterior (not shown), and in some embodiments one or both of the covers110 can be positioned, and moved, about the hinges 304 to beperpendicular to the sun's rays to maximize the collection of solarenergy.

Business Methods of Operation

FIG. 4 is a data flow diagram illustrating information flow from acustomer requesting data to a customer support center, an operationalsupport center, a UAV in a UAV pod, and back again. A customer maysubmit a data request 400, such as a request for a geographic aerialsurvey, to a customer support center. The customer support center maywork with the customer and received data to finalize the data requestfor transmission 402 to an operational support center. The operationalsupport center may use the finalized data request to determine thelocation of a launch site in or adjacent to a UAV pod survey site, toplan a plurality of flight missions that collectively accomplish thecustomer's geographic survey data request. The resultant missions plandata may then be provided 404 to a UAV pod that may be deployed to thelaunch site. Prior to launch, the first of the plurality of missions isprovided to the UAV 406 in the form of flight data, such as altitude,heading, and way points, and the UAV is launched to perform the mission.Upon return of the UAV to the UAV pod, the survey raw data, such ascamera imagery, event logs, GPS and IMU raw data, may be provided 408 tothe UAV pod. In one embodiment, the UAV pod may pre-process the data,such as by converting the raw data into viewable JPGs with anaccompanying geospatial location. Additional pre-processing may beperformed, such as stitching the images into an orthomosaic. In afurther embodiment, such pre-processing may be performed onboard the UAVprior to providing the data to the UAV pod. The pre-processed data maybe provided 410 to the customer support center for final processing.

The next mission's flight data may be provided 412 to the UAV and theUAV may be launched to perform the next survey mission. Upon its return,the survey raw data may be provided 414 to the UAV pod forpre-processing and the pre-processed data may then be provided 416 tothe customer support center for additional processing. With the UAVreceiving the last mission flight data 418 and upon receipt by the UAVpod of the final survey raw data 420, the final pod-processed data maybe provided 422 to the customer support center. After final processingof the collective missions pre-processed data, the survey results may beprovided 444 by the Customer Support Center to the customer.

FIG. 5 is a data flow diagram illustrating another embodiment of theflow of information from a customer requesting data, to a customersupport center to an operational support center, to a UAV in a UAV podand back again to the customer. As illustrated above, the customer maysubmit the data request 500 to the customer support center that may thenfinalize the data request for transmission 502 to an operational supportcenter. The processed requested data is used to develop a plurality offlight missions that collectively accomplish the customer's datarequest. The resultant missions plan data may then be provided 504 tothe UAV pod that may deployed to the launch site, and the firstmission's flight data provided 506 to the UAV prior to launch andaccomplishment of the first flight survey mission. The pre-processedsurvey data may be provided 508 to the UAV pod for storage, and thesecond mission's flight data provided 510 to the UAV to conduct thesecond mission's survey. Upon returning to the UAV pod, the secondmission's pre-processed flight data may be provided 512 to the UAV pod.After the last mission's flight data is provided 514 to the UAV by theUAV pod and after conclusion of the last flight mission survey, the lastmission's flight survey data may be provided 516 to the UAV pod and thecollective missions' pod-processed survey data provided 518 to thecustomer support center for final processing before providing 520 thefinally-processed survey data to the customer.

FIG. 6 is a flow diagram illustrating one embodiment of use of the UAVpod and UAV system by a customer. A first data request is received froma customer, such as an owner of an agricultural field or land usemanager (block 600). The customer may input the data request through awebsite portal that requests information detailing the request. Forexample, the customer may wish to provide geographic boundaries tosurvey a first geographic coverage area during a specific period of timeto accomplish a refresh rate. “Refresh rate” refers to the number oftimes each area of the geographic coverage area is imaged during thedeployment period for that geographic coverage area. In otherembodiments, the data request may include a ground resolution or groundsurface distance (“GSD”). For example, a GSD of one inch may enable thecoverage areas and refresh rates described in Table 1.

TABLE 1 Example 1 Example 2 Example 3 UAV Deployment 90 days 90 days 90days Period UAV Missions    360   360   360 GSD 1 inch 1 inch 1 inchCoverage Area 100,000 12,500 6,250 Refresh Rate 1 (once/ 8 (once/ 16(once/ 90 days) 11 days) 6 days)

Similarly, by suitably modifying GDS values, the UAV may have thecoverage area and refresh rates listed in Table 2.

TABLE 2 Example 4 Example 5 Example 6 Example 7 UAV Deployment 90 days90 days 90 days 90 days Period UAV Missions    360   360   360   360 GSD2 inch 4 inch 0.5 inch 0.25 inch Coverage Area 100,000 12,500 50,00025,000 (acres) Refresh Rate 2 (once/ 4 (once/ 1 (once/ 1 (once/ 45 days)23 days) 90 days) 90 days)

In other embodiments, rather than inputting the data request through awebsite portal, the customer may provide the data through a proprietarysoftware interface or via a telephone interview mechanism, each incommunication with a customer support center. A plurality of flightmissions may then be planned that collectively accomplish the customer's(block 602) request such as by pre-planning how many flights and fromwhat general areas they need to operate. The planned flight missions,such flight missions including flight mission data representing takeoffday/time, waypoints, flight altitudes, flight speeds, and such, areprovided to the UAV pod (block 604) for future communication to a UAVseated in the UAV pod.

The UAV pod may then be deployed to a launch site that is either withinor adjacent to the customer—desired geographic coverage area (block606). Deployment may consist of loading the UAV into a UAV pod andtransporting both to the launch site by means of truck or aircrafttransport. By way of further example, the UAV pod and enclosed UAV maybe transported by a commercial carrier (e.g., FedEX, UPS, etc.) to afarm for offloading into a field, or by an oil and gas utility companyto a location adjacent a transmission or pipeline that may be thesubject of a visual survey. The UAV may be provided with flight missiondata representing one of the plurality of missions (block 608) such asby short range wireless or wired communication within the UAV pod. TheUAV may then be launched out of the UAV pod to perform the providedflight mission (block 610). As described herein, a “mission” or “flightmission” preferably encompasses one launch, survey flight, and landing,but may encompass more than one launch/flight/landing. The flightmission data may also include dynamic flight instructions, such asaltering its trajectory, attitude or such as by dropping a payload ifcertain conditions exist, such as would be valuable in a search andrescue mission if the plan locates the sought after object or person.

After completion of the flight mission, or in response to a reroutingrequest received by the UAV, the UAV is received in the UAV pod and theflight survey data is provided to UAV pod memory (block 612). In analternative embodiment, rather than returning to the original UAV pod,the UAV flies to and is received by a second UAV pod (block 614). Suchan alternative embodiment may be utilized in order to transition the UAVinto an adjacent geographic survey region for receipt of a new pluralityof missions for a second geographic survey. Alternatively, such anembodiment may be used to provide for an extended geographic areasurvey, one that would ordinarily not be accomplished with a single UAVdue to the UAVs inherent power/range limitation. If all missions in theplurality of missions have not yet been completed (block 616), then thenext one of the plurality of missions is provided to the UAV (block 608)and the UAV is again launched out of the UAV pod autonomously (i.e.,without human intervention) to perform the next survey flight missionand the UAV may return to the UAV pod after completing the flightmission and the recorded survey data provided to the UAV pod. Otherwise,if all missions are completed (block 616), then the completed flightsurvey data may be provided from the UAV pod (block 618). The surveydata may be provided to UAV pod memory that is in the form of detachablememory in the UAV pod, such as SD cards, USB flash memory, or otherwisedetachable and portable memory, to a UAV pod servicer, or may beprovided wirelessly through a cell phone connection, WLAN or LANconnection, or satellite—enabled transceiver. In an alternativeembodiment, the UAV is routed to a LAN area for the LAN to receive theflight survey data wirelessly during flight and before returning forlanding in the UAV pod (block 619).

As shown in FIG. 6, the UAV pod (which may now include the UAV) may thenbe retrieved and returned to an operations support center (block 620). Asecond plurality of flight missions may then be uploaded into the UAVpod to accomplish a second data request from the same or a differentcustomer and the UAV pod re-deployed. In an alternative embodiment,rather than returning the UAV pod to a support center, the UAV pod maybe moved or migrated (block 622) to a second or next geographic coveragearea for further use.

In a further alternative embodiment, the UAV pod may be deployed to alaunch site prior to providing the UAV pod with flight missions datarepresenting the planned flight missions. In such a scheme, the UAV podmay establish or join a local LAN connection for receipt of the plannedflight missions on-site.

FIG. 7 shows a pod 700 that due to its rural location lacks a wirelessdata connection and the UAV 2602 has flown from its pod 700 to loiterabove a house 703 to be within range of the house's WiFi connection.This allows the UAV 2602 to download data to either a server at thehouse 703 or to another location via an Internet connection. The UAV 702can either store the data on board and then transmit it via the WiFiconnection or relay a signal from the pod 700 to the WiFi.

FIG. 7 also shows that the UAV 702 could also transmit information bymeans of a physical act, such as loitering over an event of interestdetermined by the prior collection and processing of data. One exampleof such an event of interest could be the location of a lost person 704or the location of an area of farmland that need additional water.

The flight survey data provided to UAV pod memory (perhaps detachablememory), provided wirelessly from the UAV pod, or even provided to alocal LAN as described above, may be in raw or pre-processed form. Forexample, the flight survey data may simply be “zipped” and relayed to aremote processing station where all of the data is processed.Pre-processing the flight survey data prior to providing such from theUAV pod or directly from the UAV provides advantages, however. Datatransmission bandwidth requirements may be reduced from what wouldotherwise be needed to transmit raw data for processing to anoperational support center. A reduction in transmission bandwidthrequirements may translate into reduced data transmission costs andtime. In a preferred embodiment, either the UAV processor 208 (see FIG.2) or UAV pod processor 114 (see FIG. 1) may pre-process theUAV-captured raw data (e.g., block 618, see FIG. 4). The UAV-capturedraw data such as camera imagery, event logs, GPS and IMU raw data may beconverted into viewable JPGs with accompanying geospatial location(i.e., “geo-tagging”) for transmission. However, additionalpre-processing may be performed either by the UAV processor or UAV podprocessor. For example, the JPG images and accompanying geospatiallocation may be further processed to stitch the images into anorthomosaic so that what is sent from the UAV pod or from the UAV itselfis a single high resolution image covering the entire flight survey area(or from an individual flight mission) resulting in the lowest bandwidthneeded for transmission and the highest level of automation ofpre-processing for the ultimate customer for measuring roads, buildings,fields, identifying agricultural progress, inspecting infrastructure,urban planning, and other analysis.

As shown in FIG. 7, the UAV pod 700 may include an interface and display705 to provide the collected data and processed data for use at sitewithout the need for transmission from the pod 700 to an offsitelocation. For example, the display 705 may be used to inform local users(e.g., farmhands) of areas that need additional watering or the like.

Local UAV Operation

FIG. 8 is a flow diagram illustrating one embodiment of a method ofconducting flight missions for the UAV. The UAV may be provided with oneof the plurality of missions (block 800) that reside in the UAV pod. TheUAV may be launched vertically out of the UAV pod (block 802),preferably under its own power using the two rotors on the UAV. In oneembodiment, the immediate environment over the UAV pod is monitored forobstacles and weather (block 804) that may otherwise interfere withlaunch of the UAV. In such an embodiment, if no obstructions aredetected (block 806), then the UAV may be launched out of the UAV pod(block 802). Otherwise, launch of the UAV is delayed or cancelled andthe UAV pod continues to monitor for overhead obstacles and weather(block 804, 806), as well as the UAV battery status (block 810). Afterlaunch, the UAV pod may monitor the UAV's trajectory (block 808). If UAVbattery power is low or otherwise drops below a predetermined voltagethreshold (block 812), then the UAV pod may provide reroutinginstructions to the UAV (block 814) to shorten the current mission toenable a safe return of the UAV to the UAV pod. In an alternativeembodiment, the UAV is directed to return immediately to the UAV pod(block 816) or to an intermediate pre-determined position. If, however,the battery is not low (block 812), and no other flight warningcondition is triggered (block 818) the mission continues (block 820). Ifthe current UAV mission has been completed (block 820), the UAV returnsto the UAV pod (block 816) for landing and the geographic survey data isdownloaded to the UAV pod memory (block 822) such as by a wireless orwired transfer of the mission data to the UAV pod memory. The UAV podprotective cover may be closed (block 824) to protect the UAV from theexternal environment (i.e., rain, direct sun, vandals, or damagingparticulate matter).

Methods of General Survey Use—Contiguous Survey Areas

While embodiments of the system thus far are described within thecontext of a flight survey using only one UAV pod, it is contemplatedthat a customer of the system may request a geographic coverage areathat extends beyond the capabilities of a single UAV and UAV podcombination. FIG. 9 is a block diagram illustrating the use of aplurality of UAV pods with only one UAV to extend the possiblegeographic survey area from what would otherwise exist with only oneUAV. An operator of the system may review the customer request andallocate n number of UAV pods for deployment at a given UAV pod spacing.An extended geographic survey area 900 may thus be divided into aplurality of individual geographic survey areas 902 for mission planningpurposes. A respective plurality of UAV pods (each indicated by an ‘X’)may be deployed in predetermined launch locations so as to substantiallycover the extended geographic survey area 900 and a communicationnetwork established to allow a single human manager to monitor the setupof the entire network of UAV pods. The size of each coverage or surveyarea 902 and the positioning of the pods across the area 900, may varyby a variety of factors including the range, flight time, recharge time,sensor or sensors of the UAV to be employed in that area 902, thefrequency of the survey, the weather or season (as they may affectperformance of the UAV and/or the charging capabilities of the pod),obstacles and obstructions, wireless communications between the pod andeither the UAV, other pods, cellular network, or other radio system,dispersion of other pods in adjacent areas, and the like. Thepositioning of the pods may also be affected by the ability to positionor deliver the pods to desired locations given the accessibilityprovided by local roads and terrain. A UAV pod 904 having a pre-loadedUAV may be deployed having a plurality of preloaded missions that arecollectively sufficient to survey the immediately—surrounding coveragearea 906. After the UAV has autonomously completed the missions tosurvey the immediately—surrounding coverage area 906, the UAV 908 may betransitioned to the next predetermined UAV pod 910 for recharging (orrefueling) and to receive the first of a next plurality of flightmissions to cover the second immediately—surrounding coverage area 912.Through the use of a plurality of missions designed specifically tocollectively cover the second coverage area 912, the UAV may thenmigrate to the next coverage area 914 and so on until the entireextended coverage area 900 has been surveyed. In one embodiment, anon-coverage area 916, such as a lake, mountain, forest, city, non-farmland, or other area that is not of interest, is included in the extendedcoverage area 900 and may be avoided from survey activities to possiblyextend the serviceable area for the UAV.

In an alternative embodiment that recognizes the autonomous landingcapability of the UAV, the UAV, rather than transitioning to the nextindividual geographic survey area 902 or to the next individualgeographic survey areas 902, the UAV may fly to a predetermined dataoffloading waypoint, such as a customer's farm house or automobile, toestablish or join a local LAN connection or to establish a wirelessconnection to provide a data dump of geographic survey data.

In a further alternative embodiment, more than one UAV may be providedwithin the extended geographic survey area 900, with each UAV having adifferent sensor suite to gather complementary data for the customer. Insuch a scheme, each UAV may survey the entire extended geographic surveyarea 900 by transitioning through the plurality of individual geographicsurvey areas 902 over time, or to only a subset of each area 900, toobtain a more complete understanding of the area 900 than would bepossible with only a single UAV sensor suite.

Also, although the prior description describes one UAV for each UAV pod,in an alternative embodiment, each UAV pod may selectively encompass,provide power for, and distribute missions to two or more VTOL UAVs. Insome embodiments, each pod deployed to a survey area 902 will includeits own UAV to allow the given area 902 to be surveyed at the same time,or about the same, time or frequency as any other area 902. UAV pods indifferent areas 902 could contain UAVs with different sensors, or sensorsuites, and the UAV pods could trade UAVs as necessary to obtain thedesired sensor coverage.

Although FIG. 9 illustrates each immediately—surrounding coverage area(e.g., 906, 912, 914) as being circular, a UAV pod and associated UAVmay be provided with a plurality of missions that cover a rectangularcoverage area 1000 (see FIG. 10) or a coverage area having differentregular or irregular shapes to accomplish the overall goal of surveyingan extended coverage area 1002 that could not otherwise be coveredwithout the use of multiple UAVs or with UAVs having significantlygreater range capabilities, as illustrated in FIG. 10.

Methods of General Survey Use—Non-Contiguous Survey Areas

FIG. 11 illustrates two extended coverage survey areas that may beserviced using only one UAV or a limited number of UAVs. The twoextended coverage survey areas (1102, 1104) are not contiguous, butrather are separated into two distinct extended coverage areas. During amission planning procedure, each of the two extended coverage surveyareas (1102, 1104) are broken up into perspective area sets 1106 thatare serviceable with a single UAV/UAV pod set. In such an arrangement, asingle UAV may transition from one area set 1106 to the next within thefirst extended coverage survey area 1102 as the respective missions arecompleted, until transitioning to the next extended coverage survey area1104.

While various embodiments of the invention have been described, it willbe apparent to those of ordinary skill in the art that many moreembodiments and implementations are possible that are within the scopeof this invention.

What is claimed is:
 1. An unmanned aerial vehicle (UAV) operationalsystem, comprising: a UAV pod having a pod memory and a pod processor,the pod memory storing a first plurality of UAV flight missioninformation that is adequate to survey a geographic coverage area at apredetermined refresh rate; and a UAV seated in the UAV pod, the UAVhaving a UAV memory storage and a UAV processor, the UAV memory storingone of the first plurality of UAV flight missions; wherein each one ofthe plurality of UAV flight missions represents a launch, survey andlanding of the UAV.
 2. The system of claim 1, further comprising: surveydata from at least one of the first plurality of UAV flight missionsstored in the pod memory.
 3. The system of claim 1, further comprising:survey data from at least one of the first plurality of UAV flightmissions stored in a second pod memory.
 4. The system of claim 3,wherein the second pod memory comprises portable memory detachablyconnected to the UAV pod.
 5. The system of claim 3, wherein the UAV podfurther comprises a transceiver in communication with the pod processor,the pod processor configured to transmit the survey data to anoperational support center positioned remotely from the UAV pod.
 6. Thesystem of claim 1, further comprising: a customer support centerconfigured to receive a first data request from a customer viaelectronic communications and wherein the first data request furthercomprises: a first geographic coverage area; and a refresh rate for thefirst geographic coverage area.
 7. The system of claim 6, wherein thefirst data request further comprises one of a ground resolution orground sample distance (GSD).
 8. The system of claim 1, furthercomprising: a transceiver in the UAV, the transceiver configured tocommunicate with the UAV pod.